Skip to content

Add ability to force upgrades even when Nextcloud version did not change #2403

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

boomer41
Copy link

@boomer41 boomer41 commented Mar 2, 2025

We'd like to bundle custom apps into the image by extending it.
However, we ran into issues when we want to push an update to an app in the image when the Nextcloud version did not change.

We solved that by

  • adding a new hook called pre-initialization that runs even before the need for an initialization/upgrade is determined, and
  • by forcing an initialization run when a marker file /tmp/nextcloud-force-initialization exists.

The later can be dynamically created by a script triggered the new hook mentioned above.
With this setup, the script can then additionally start an initialization run.
When the initialization is finished, the marker file is automatically removed.
The script can not stop an upgrade from happening, it can only additionally start one.

boomer41 added 3 commits March 2, 2025 09:55
Allow execution of scripts even before the need to install or update
Nextcloud is determined. Useful when needing to have additional update
condition checks.

Signed-off-by: Stephan Brunner <s.brunner@stephan-brunner.net>
… tmp folder

We have a custom image where we'd like to recopy all of nextcloud's
source code again when we update some internal thing without a change in
Nextcloud's version. The newly added pre-initialization hook can be used
to determine this and force a rerun.

Signed-off-by: Stephan Brunner <s.brunner@stephan-brunner.net>
Signed-off-by: Stephan Brunner <s.brunner@stephan-brunner.net>
@boomer41
Copy link
Author

boomer41 commented May 4, 2025

Any updates on this PR from the maintainers? :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant